Interface
Part 1/6 • 18.6 KB total
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Manual: Interfaces ↗
An interface is how a Reticulum instance communicates with the outside world.
The interface system is medium-agnostic, so an instance can use a mix of local communication hardware, remote public endpoints and virtual interfaces. See the list of interface types below.
Contents
Configuration
In RNS, interfaces are specified in the configuration file under [interfaces]. See Common Interface Options ↗ in the manual for more.
Getting started
To connect to the global Reticulum backbone, simply add one or more public endpoints from directory.rns.recipes or rmap.world.cite-ref-1[1]
Rather than relying on static connections, consider using public endpoints as temporary bootstrap connections that dynamically discover and auto-connect to more suitable ones. This results in a network topology that is more geographically relevant, resilient and efficient. This is the way.cite-ref-2[2]
Note: Reticulum is not a single global network you “join”. It's a toolkit for building all sorts of networks, small or large. How you choose to connect to other peers is up to you.cite-ref-3[3]
Recommended reading
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────